Skip to content

Conversation

@stockholmux
Copy link
Member

Description

Initial version of the blog for the 9.0 release.

I ran into a few issues that I could use some help with:

  1. The atomic slot migration paragraphs were me writing up with @PingXie said at Keyspace. It could use a pretty complete review to make sure I captured the story completely and accruately.
  2. I based the 'much, much, more' section on a slide from Keyspace. I tired to hunt down the related PRs but there were a few that I couldn't pin down ('1000+ node cluster', and 'Zero copy responses'). I specific PR link would make this stronger.

Issues Resolved

#312

Check List

  • Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the BSD-3-Clause License.

Signed-off-by: Kyle J. Davis <kyledvs@amazon.com>
@stockholmux stockholmux requested a review from madolson as a code owner October 12, 2025 06:07
Copy link
Member

@madolson madolson left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The technical details look pretty good

stockholmux and others added 2 commits October 14, 2025 10:42
Co-authored-by: Madelyn Olson <madelyneolson@gmail.com>
Signed-off-by: Kyle J. Davis <kyledvs@amazon.com>
Co-authored-by: Madelyn Olson <madelyneolson@gmail.com>
Signed-off-by: Kyle J. Davis <kyledvs@amazon.com>
stockholmux and others added 2 commits October 14, 2025 11:27
Signed-off-by: Kyle J. Davis <kyledvs@amazon.com>
Co-authored-by: Madelyn Olson <madelyneolson@gmail.com>
Signed-off-by: Kyle J. Davis <kyledvs@amazon.com>
Copy link
Member

@madolson madolson left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I feel like what is left is subjective, I think as is the blog looks fine.

Co-authored-by: Madelyn Olson <madelyneolson@gmail.com>
Signed-off-by: Kyle J. Davis <kyledvs@amazon.com>
Signed-off-by: Kyle J. Davis <kyledvs@amazon.com>
@madolson madolson moved this to Todo in Valkey 9.0 Oct 20, 2025
@stockholmux stockholmux merged commit ada8522 into valkey-io:main Oct 21, 2025
3 checks passed
@github-project-automation github-project-automation bot moved this from Todo to To be backported in Valkey 9.0 Oct 21, 2025
stockholmux pushed a commit that referenced this pull request Oct 23, 2025
This PR adds a banner to the top of the Valkey website announcing the
release of Valkey 9.0 and linking to the release blog post (PR #390).

## Changes

- Added banner configuration to `config.toml` with a concise message
about Valkey 9.0
- The banner links to the blog post at `/blog/introducing-valkey-9/`
- Uses the existing banner infrastructure (templates, styling, and
JavaScript) already present in the website

## Banner Features

- **Message**: "What's new in Valkey 9.0? Discover new features and
improvements."
- **Dismissible**: Users can close the banner using the X button on the
right
- **Persistent**: Banner dismissal is remembered in localStorage for 24
hours
- **Responsive**: Works across all pages and devices, displays on a
single line without wrapping

## Screenshot

<img
src="https://github.com/user-attachments/assets/d559710e-5e0d-44af-847f-7f9128b5f881">

The banner appears at the top of every page with white text on a purple
background (#2D2471), consistent with the existing banner design system.

## Implementation Note

This implementation leverages the complete banner system that was
already built into the website templates. No template, styling, or
JavaScript changes were needed - only the configuration value was added
to enable the banner.

Fixes #398

<!-- START COPILOT CODING AGENT SUFFIX -->



<details>

<summary>Original prompt</summary>

> 
> ----
> 
> *This section details on the original issue you should resolve*
> 
> <issue_title>Add a new banner for a what's new for Valkey
9.0</issue_title>
> <issue_description>Add a banner to the top of the Valkey website that
includes what's a link to the new unpublished blog post
#390.
</issue_description>
> 
> ## Comments on the Issue (you are @copilot in this section)
> 
> <comments>
> </comments>
> 


</details>

Fixes #398

<!-- START COPILOT CODING AGENT TIPS -->
---

✨ Let Copilot coding agent [set things up for
you](https://github.com/valkey-io/valkey-io.github.io/issues/new?title=✨+Set+up+Copilot+instructions&body=Configure%20instructions%20for%20this%20repository%20as%20documented%20in%20%5BBest%20practices%20for%20Copilot%20coding%20agent%20in%20your%20repository%5D%28https://gh.io/copilot-coding-agent-tips%29%2E%0A%0A%3COnboard%20this%20repo%3E&assignees=copilot)
— coding agent works faster and does higher quality work when set up for
your repo.

---------

Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com>
Co-authored-by: madolson <34459052+madolson@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: To be backported

Development

Successfully merging this pull request may close these issues.

3 participants